{"id":13077,"date":"2018-12-06T21:59:20","date_gmt":"2018-12-06T21:59:20","guid":{"rendered":"https:\/\/www.gravityforms.com\/?p=13077"},"modified":"2021-05-10T20:10:59","modified_gmt":"2021-05-11T00:10:59","slug":"gutenberg-and-gravity-forms","status":"publish","type":"post","link":"https:\/\/www.gravityforms.com\/blog\/gutenberg-and-gravity-forms\/","title":{"rendered":"WordPress 5.0, Gutenberg, and Gravity Forms"},"content":{"rendered":"

\"Typewriter<\/p>\n

As you’ve likely already heard, WordPress 5.0\u00a0includes Gutenberg; an entirely new publishing experience. In the past, we’ve discussed Gutenberg<\/a> quite a bit and think it’s a great opportunity to robust content. In fact, we were not only one of the earliest adopters of Gutenberg when we created our Gutenberg block for Gravity Forms, but we’ve also been active contributors to the project for quite a while.<\/p>\n

<\/p>\n

How Does Gutenberg Impact Gravity Forms Users?<\/h2>\n

At the moment, standard Gravity Forms installations won’t see much of a difference. You’ll still have the same form creation and editing experience that you’ve always known.<\/p>\n

When it comes to embedding forms into posts or pages, you will see a few changes. Since the default WordPress post editor is being changed, you might notice that the\u00a0Add Form<\/em> button is no longer in its standard place.<\/p>\n

A New Experience When Embedding New Forms<\/h3>\n

Within the old WordPress post editor, clicking on the\u00a0Add Form<\/em> button would allow you to select your form and options, then insert the Gravity Forms shortcode into your page. Due to the area no longer existing, the button will no longer be there when using the new Gutenberg editor. This leaves you with a few different options for embedding your forms:<\/p>\n

    \n
  1. Place the Gravity Forms shortcode<\/a> within a Gutenberg shortcode block.<\/li>\n
  2. Install the optional Gravity Forms Gutenberg block from the Downloads page<\/a> or on GitHub<\/a>.<\/li>\n
  3. Go back to the old post editor using the Classic Editor plugin<\/a>.<\/li>\n<\/ol>\n

    Of course, as Gutenberg matures, we’ll be further integrating Gravity Forms with Gutenberg to gain a more seamless experience directly within the core Gravity Forms plugin.<\/p>\n

    The Future of Gutenberg Support in Gravity Forms<\/h3>\n

    Over the years, Gravity Forms has become the go-to WordPress form plugin for businesses who rely on stability, security, and compatibility. With larger adoption than any other WordPress form plugin on the market, especially amongst enterprise clients, we want to ensure that anything we do is fully backwards compatible for both users and 3rd-party developers alike.<\/p>\n

    Right now, Gutenberg is still very much in a state of heavy development. Due to our customers’ high expectations, we can’t confidently merge our Gutenberg block into the core Gravity Forms plugin while still keeping our promise to provide the high-quality product that we’re known for.<\/p>\n

    We’ll be keeping an eye on things and eventually merging our Gutenberg features into the core Gravity Forms plugin, but for right now, we’ve chosen to focus on stability and extensibility.<\/p>\n

    Should I Avoid Updating to WordPress 5.0?<\/h3>\n

    We always recommend updating to the latest release of WordPress. Gutenberg aside, WordPress 5.0 does include several changes that will improve the stability and security of your site. Even if you’re not a fan of Gutenberg or aren’t ready to fully make the jump yet, you can always update and use the old post editor with the Classic Editor plugin<\/a>.<\/p>\n

    Gravity Forms will still work the same as before, with the exception of the\u00a0Add Form<\/em> button when using the Gutenberg editor. In fact, unless you’re embedding a form into a new page or post, you won’t see a difference when it comes to Gravity Forms.<\/p>\n

    Our Hopes for the Future of Gutenberg<\/h2>\n

    Moving forward, we want to see Gutenberg further mature into a stable product, as well as address the various accessibility and developer concerns that have existed for quite a while now.<\/p>\n

    Even as Gutenberg releases today in WordPress 5.0, we’re still seeing a constant flux within the Gutenberg codebase, as well as accessibility issues that can cause issues for people with various individual needs. Gutenberg has certainly been making progress, but like any other new feature, it still has some growing up to do.<\/p>\n

    As the Gutenberg project progresses and is able to address those concerns, we’ll be able to move forward with a more thorough adoption of it within Gravity Forms.<\/p>\n

    Final Thoughts<\/h2>\n

    Overall, we’re still excited about the Gutenberg project, but are still looking for a certain level of maturity that our customers require. We’re still working hard to bring some great features to Gravity Forms that will utilize the Gutenberg editor, and we believe you’ll absolutely love what we have coming in the future as Gutenberg matures.<\/p>\n

    If you have additional thoughts about Gutenberg, good or bad, we’d love to hear more from you. Leave us a comment below to keep the discussion going and with any luck, we’ll be able to work together to make WordPress and Gutenberg truly amazing.<\/p>\n","protected":false},"excerpt":{"rendered":"

    As you’ve likely already heard, WordPress 5.0\u00a0includes Gutenberg; an entirely new publishing experience. In the past, we’ve discussed Gutenberg quite a bit and think it’s a great opportunity to robust content. In fact, we were not only one of the earliest adopters of Gutenberg when we created our Gutenberg block for Gravity Forms, but we’ve also been active contributors to the project for quite a while.<\/p>\n","protected":false},"author":204039,"featured_media":13078,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\n\n\n\n\t\n\t\n\t\n